Fixes bug https://microsofthealth.visualstudio.com/Health/_workitems/edit/138656

If all clocks (i.e. clocks of processing clients and the database clock) are synchronized, explicit input lastUpdated on the ingested resource should always be either in the past or current relative to the database clock. This rule is important in order to guarantee that records without explicit lastUpdated (when they are processed in parallel with records with explicit lastUpdated) are loaded with correct versions and history flags in the database. To facilitate this logic, input parser rejects records with explicit lastUpdated pointing too far in the future (>10 seconds). 10 seconds "future tolerance" should be more than enough for current computer systems. "Future tolerance" interval cannot be arbitrary large to minimize number of retries required to land input records without explicit lastUpdated after latest records in the database.